Google Git
Sign in
gerrit / git-repo / refs/tags/v2.53
tag2bf2c96cbb84084e6ee9537778e07892e5189146
taggerGavin Mak <gavinmak@google.com>Tue Mar 18 21:56:57 2025 +0000
object4b94e773efd36754f6c8649ad55b90d19a61107f 
repo v2.53
commit4b94e773efd36754f6c8649ad55b90d19a61107f[log] [tgz]
authorAlbert Akmukhametov <arakmukhametov@salutedevices.com>Mon Feb 17 17:04:42 2025 +0300
committerLUCI <gerrit-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Mar 13 09:12:45 2025 -0700
tree440f35763639becf735b12a770b1783dfc6700ba
parentfc901b92bbcde2c16cd557322041abf958297665 [diff]
Sync: Fix full submodule sync while shallow specified

Git allows to clone submodules as shallow clone [1]. On the other
hand, when repo synchronize a projcet with submodules inside, it
ignores the shallow parameter.

When a project contains submodules, project.py parses the .gitmodules
file for URL and path. This parsing does not consider the shallow
option. Consequently, this parameter is not propgated to newly
created Project instance for that submodule.

[1] https://git-scm.com/docs/gitmodules#Documentation/gitmodules.txt-submoduleltnamegtshallow

Change-Id: I54fc9c69ae1b8e3cda2801202e3f0c7693b718d2
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/454261
Tested-by: Albert Akmukhametov <alb.02057@gmail.com>
Commit-Queue: Albert Akmukhametov <alb.02057@gmail.com>
Reviewed-by: Josip Sokcevic <sokcevic@chromium.org>
Reviewed-by: Никита Сказкоподателев (Nask) <skazkopodatelev@gmail.com>
1 file changed
tree: 440f35763639becf735b12a770b1783dfc6700ba
  1. .github/
  2. docs/
  3. hooks/
  4. man/
  5. release/
  6. subcmds/
  7. tests/
  8. .flake8
  9. .gitattributes
  10. .gitignore
  11. .gitreview
  12. .isort.cfg
  13. .mailmap
  14. .project
  15. .pydevproject
  16. color.py
  17. command.py
  18. completion.bash
  19. constraints.txt
  20. editor.py
  21. error.py
  22. event_log.py
  23. fetch.py
  24. git_command.py
  25. git_config.py
  26. git_refs.py
  27. git_ssh
  28. git_superproject.py
  29. git_trace2_event_log.py
  30. git_trace2_event_log_base.py
  31. hooks.py
  32. LICENSE
  33. main.py
  34. MANIFEST.in
  35. manifest_xml.py
  36. pager.py
  37. platform_utils.py
  38. platform_utils_win32.py
  39. progress.py
  40. project.py
  41. pyproject.toml
  42. README.md
  43. repo
  44. repo_logging.py
  45. repo_trace.py
  46. requirements.json
  47. run_tests
  48. run_tests.vpython3
  49. setup.py
  50. ssh.py
  51. SUBMITTING_PATCHES.md
  52. tox.ini
  53. wrapper.py
README.md

repo

Repo is a tool built on top of Git. Repo helps manage many Git repositories, does the uploads to revision control systems, and automates parts of the development workflow. Repo is not meant to replace Git, only to make it easier to work with Git. The repo command is an executable Python script that you can put anywhere in your path.

Contact

Please use the repo-discuss mailing list or issue tracker for questions.

You can file a new bug report under the “repo” component.

Please do not e-mail individual developers for support. They do not have the bandwidth for it, and often times questions have already been asked on repo-discuss or bugs posted to the issue tracker. So please search those sites first.

Install

Many distros include repo, so you might be able to install from there.

# Debian/Ubuntu.
$ sudo apt-get install repo

# Gentoo.
$ sudo emerge dev-vcs/repo

You can install it manually as well as it's a single script.

$ mkdir -p ~/.bin
$ PATH="${HOME}/.bin:${PATH}"
$ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/.bin/repo
$ chmod a+rx ~/.bin/repo